IP Enrichment - DomainTools Parsed Whois

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

This playbook uses the DomainTools Parsed Whois API. Given a ip address or set of ip addresses associated with an incident, return Whois information data for the extracted ip addresess as comments to the incident.

Attribute	Value
Type	Playbook
Solution	DomainTools
Source	View on GitHub

Additional Documentation

📄 Source: DomainTools-IP-Address-Playbook/readme.md

DomainTools IP Address Enrichment Playbook

Overview
Deploy DomainTools-IP-Address-Playbook
Authentication
Prerequisites
Deployment
Post Deployment Steps

Overview

This playbook uses the DomainTools Parsed Whois API. It is able to provide whois information for a IP or set of IPs associated with an incident.

Visit https://www.domaintools.com/integrations to request a Api key.

When a new Azure Sentinel Incident is created, and this playbook is triggered, it performs these actions:

It fetches all the IP entities in the Incident.
Iterates through the IP entities and fetches the results from Parsed Whois for each entity.
All the details from DomainTools Parsed Whois will be added as comments in a tabular format.

Links to deploy the DomainTools IP Address Playbook

Authentication

Authentication methods this connector supports: - API Key authentication

Prerequisites

A DomainTools API Key
DomainTools Function App should be deployed

Deployment instructions

Deploy the playbooks by clicking on "Deploy to Azure" button. This will take you to deploying an ARM Template wizard.
Fill in the required parameters for deploying the playbook.
Click "Review + create". Once the validation is successful, click on "Create".

Post-Deployment instructions:

As a best practice, we have used the Sentinel connection in Logic Apps that use "ManagedSecurityIdentity" permissions. Please refer to this document and provide permissions to the Logic App accordingly.

b. Configurations in Sentinel:

In Azure Sentinel, analytical rules should be configured to trigger an incident with risky IP Address indicators.
Configure the automation rules to trigger the playbook.